-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP on desired bindgen
output
#93
Conversation
Another random idea: Add a new macro that makes it possible to still use the "familiar" msg_send_2![self, getObjects: vec.as_ptr(), range: range]
// ->
self.getObjects_range_(vec.as_ptr(), range) This would require the |
3457bd3
to
4d04ab1
Compare
dd1cd75
to
e26f51f
Compare
e26f51f
to
795d83d
Compare
795d83d
to
272fd53
Compare
272fd53
to
819d96d
Compare
The biggest problem I had with this approach was that the separation between a Future work in this problem space is happening in #264 |
Progress on evaluating if and/or how we should do #85.
Don't look too much at the
objc2-foundation-sys
stuff, the idea is that that part would be automatically generated - rather, focus onobjc2-foundation
, and think about whether using the bindings is better or worse.